The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 7, 2026 10:41pm

PR Summary

Medium Risk
Changes when table insert side-effects (triggers/scheduling) run and how schema updates are constructed, which can affect workflow execution timing and downstream consumers. Scope is limited to CSV import and batch insert paths but touches core table write behavior.

Overview
Fixes two CSV-import-related table bugs.

addTableColumnsWithTx now preserves non-column schema fields (e.g. workflowGroups) when adding columns, avoiding silent loss of schema config during CSV-driven column creation.

Insert side-effects are moved to a new dispatchAfterBatchInsert helper and are invoked after the surrounding transaction commits (both in batchInsertRows and the CSV import append flow), ensuring fireTableTrigger/scheduleRunsForRows see the newly inserted rows. Tests for the import route are updated to mock this new dispatch.

^{Reviewed by Cursor Bugbot for commit 50817dc. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

This PR patches two related bugs in the table CSV-import path. addTableColumnsWithTx was reconstructing the schema object from scratch, silently dropping workflowGroups and any other top-level schema fields on every CSV column-add; the fix spreads table.schema first. batchInsertRowsWithTx was firing fireTableTrigger and scheduleRunsForRows from inside the caller's transaction, where the global DB connection could not yet see the committed rows; dispatch is now extracted into dispatchAfterBatchInsert and called by both the non-tx wrapper (batchInsertRows) and the CSV append route after db.transaction resolves.

• service.ts: Schema spread preserves workflowGroups; dispatchAfterBatchInsert is the new public helper that callers invoke post-commit.
• route.ts (append mode): Accumulates all inserted rows inside the transaction, then fires dispatch once after the transaction commits using the updated working table (correct schema for trigger context).
• route.test.ts: Wires dispatchAfterBatchInsert into the service mock but omits assertions in happy-path tests that it was invoked.

Confidence Score: 4/5

Safe to merge — both bug fixes are well-scoped and correct; the only gap is a missing assertion in the test suite.

The schema spread in addTableColumnsWithTx correctly preserves workflowGroups, and dispatchAfterBatchInsert is called after db.transaction resolves in both the non-tx wrapper and the CSV append route. The only weak spot is that route.test.ts registers mockDispatchAfterBatchInsert but never asserts it was called, so a future regression dropping the dispatch call would go undetected.

apps/sim/app/api/table/[tableId]/import/route.test.ts — happy-path tests should assert dispatchAfterBatchInsert is invoked

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Route as CSV Import Route
    participant DB as db.transaction
    participant Service as service (Tx helpers)
    participant Trigger as fireTableTrigger / scheduleRunsForRows

    Route->>DB: begin transaction
    DB->>Service: addTableColumnsWithTx (schema spread fix)
    Service-->>DB: updated table (workflowGroups preserved)
    DB->>Service: batchInsertRowsWithTx x N batches
    Service-->>DB: allInserted rows
    DB-->>Route: inserted rows + finalTable
    Note over DB: transaction committed
    Route->>Trigger: dispatchAfterBatchInsert(finalTable, insertedRows) - runs AFTER commit

_{Reviews (1): Last reviewed commit: "fix(table): preserve workflow groups on ..." | Re-trigger Greptile}